[TIR] Check producer predicate in ReverseComputeInline
#13338
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, even if a producer block has a non-trivial predicate,
ReverseComputeInline
goes ahead and produces buggy a schedule. The real-world example I've hit was the following. AfterReverseComputeInline
thecompute_4
block, the predicate ((ax1_0 * 4 + ax1_1) * 32 + ax1_2) * 2 + ax1_3 < 64
) disappears. See https://gist.github.com/masahi/01a80b86062122ad57b9b1fd785fb960 for a repro.So we should disallow
ReverseComputeInine
when the producer has a non-trivial predicate. But if the predicate in the new inlined block can imply the original predicate in the producer block, we can still allowReverseComputeInline
to be applied. These two cases are demonstrated in the test cases.@vinx13 @junrushao @Hzfengsy